chore: add lib, mod and crate foundation for event validation #467
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
WIP : AES-27
Create the bones: structs/traits/hooks to validate events
Description
Validating an event signature is the easy part and we have more work to actually validate an event. Add the hooks so we can check the ceramic properties of an event.
This includes
validate init event signature against controller
adding data events to a queue that keeps it in memory and loads the init event (when available for recon)
validating the signature against the init event controller
validating the cacao resources
adding time events to a (possibly separate) queue that can retrieve block information and validate the root and proof